Back in 2016, Oracle announced a big change to the way updates occur for their PLM flagship, Agile. Agile PLM RUP (Release Update Packs) This news carries some weight that will impact every licensee at some point, if it has not already. It will play to your advantage if you know exactly what is means and does not mean.
The end of Agile?
We have all observed Oracle’s shift in focus and resources into the development of enterprise cloud applications. So what does this mean? First off, no, this is not the beginning of the end. This news highlights important insights for every user, especially if Oracle’s strategic shift has concerned you. It underscores the necessity of understanding these changes and their implications.
What is a Release Update Pack?
Introduced in 2017, a Agile PLM RUPs is a comprehensive patch containing defect fixes. It incorporates critical client patches since the last release, specific fixes for the RUP, and accumulates all previous RUP fixes. RUPs exclude database changes and enhancements, focusing solely on problem fixes. They are released as downloadable patches on My Oracle Support.
The Agile Update Model
Until recently, Oracle software developers would plan to make one significant Agile release each year. These waterfall updates contained minor coding fixes, requested feature and functionality, and some generic compatibility extensions.
In April 2017, Oracle began releasing Agile PLM RUP for users of versions 9.3.5 or 9.3.6, every two months.
What Does This Mean?
Let’s suppose your organization wants to stay current on Agile versions, but your current environment operates on an earlier A9 version (9.3.4, or before).
You will need to upgrade to either version 9.3.5 or 9.3.6. Now you can choose to install the latest RUP or hold off until a release that includes more applicable bug fixes and enhancements. Instead of installing several patches or possibly volatile one-off patches, a single installation will include all previous RUPs as well.
Oracle release packs as necessary, sometimes as frequently as every two months. Each new Agile PLM RUP will accompany a full list of fixes and enhancements. You can view those details in the ‘Read Me’ corresponding to that release..
Currently, this is Oracle’s road map going forward.
RUP Installations
If you are wondering if it is worth the trouble to apply the RUPs to your Agile environments, my answer is, absolutely- without a doubt.
RUPs can be installed and tested with less effort, when compared to upgrading and installing a full Agile release. Customers can plan to deploy in a test environment, test system functionality, and push to Production on a streamlined timeline without worrying about prerequisites or incompatibility with previous patching.
Although RUP installs will be lighter than the weight of former updates, I recommend enlisting a competant Agile services provider for extensive testing and guaranteed project success. It’s been my experience that the headache can be quite severe with a botched upgrade implementation. Any one of a million things can go wrong.
RUP Enhancements
Although bug fixes might be the impetus to apply a specific RUP, the enhancements alone will certainly make them worth considering.
For example, here is one of the functional enhancements from the 9.3.6.4 RUP:
They are called Agile PLM RUPs (or Release Update Packs ) and the implications of this change carry some weight, both in the now, and well into the future.
Workflow notification enhancement
- Impact to Administrator
- A new property ‘Allow User to Notify Reviewers on’ is now added to each ‘Review/Release’ type workflow status.
- The property is a multiple list with 3 values: Comment, Approve/Reject, Acknowledge. Selecting a value reveals the ‘Reviewers on Current Status/Previous Status’ option in a specific popup window. Conversely, deselecting it hides this option from view. This mechanism ensures users can customize their interaction with the system based on their preferences, enhancing user experience by making features visible only when needed.
- By default, all the 3 values are selected, which means the system will behave exactly the same as is.
- When Administrator wants to block the option on any status of a certain workflow, they can de-select one or multiple values from the new property and Save.
- See more details in Product Collaboration User Guide.
- Impact to Web Client
- When user open the corresponding pop-up window in Web Client, they will find the option is invisible.
- Impact to Workflow
- The new added property can be Export/Import as well as the other workflow properties through Workflow Export/Import functionality.
- Impact to ACP
- You can migrate new property and other workflow properties through ACP script..
- Impact to Upgrade
- You can migrate new property and other workflow properties through ACP script.
- Impact to OOTB Report
- Oracle also added the new property to the Workflow Configuration Report.
- Not Supported Use Cases
- The behavior change is not applied into Java Client, which means user can still use the option to notify other reviewers if they are allowed to use Java Client to do business operations (though it is not recommended).
- Once Administrator tries to block the option on a certain workflow, he/she should manually guarantee all ‘Review/Release’ type status are set consistently. Otherwise, user may still have the chance to send out notifications to other reviewers.
Enhancing Workflow Interactions with Agile RUPs.
Are you excited by the possibilities that Release Update Packs offer? If you aim to not only keep your system current but also ensure it operates at peak efficiency, we have the ideal solution ready for you.
Explore Our Agile PLM Upgrade Services
Disclaimer: The views and opinions expressed do not necessarily reflect the views and opinions of Domain Systems. The author takes full responsibility for the views expressed here.